chore(deps): bump minio from 7.1.3 to 8.0.6 - #3559
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
|
@dependabot rebase |
Bumps [minio](https://github.com/minio/minio-js) from 7.1.3 to 8.0.6. - [Release notes](https://github.com/minio/minio-js/releases) - [Commits](minio/minio-js@7.1.3...8.0.6) --- updated-dependencies: - dependency-name: minio dependency-version: 8.0.6 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
22fefa2 to
b90fa78
Compare
|
There's a breaking change with Minio 8.0.6 in browser environments. In Minio 7.1.3, file system (fs) imports were lazy - only executed when actually needed. In Minio 8.x, they reorganized the code during the TypeScript migration and made fs imports eager. Problem: The SDK now tries to access Node.js fs module at startup, which doesn't exist in browsers. This crashes the entire SDK import. Impact: If we upgrade to Minio 8.0.6, the SDK breaks all frontend and client services that import it. Every app using our SDK will fail to load. Solution: We can add polyfills on every client service (like browserify-fs) to mock the fs module, but this adds complexity and dependencies. Alternatively, we should consider staying on Minio 7.1.3 until they fix browser compatibility in future releases. |
|
@flopez7 I might be missing something, but from what I see |
Bumps minio from 7.1.3 to 8.0.6.
Release notes
Sourced from minio's releases.
... (truncated)
Commits
212f282fix: redirect xml parser error to stream error (#1416)5f2dc07fix documentation link (#1419)ebd419etest with node v24 (#1420)eab7cb6build(deps-dev): bump form-data from 4.0.0 to 4.0.47a67d9aUpdate package.json for type definition entry point (#1315)8654c77fix: makegetBucketRegionAsyncpublic (#1413)fbcfe63fix listing bug in v1 and add missing v1 version listing (#1405)6a821b5fix tag parsing and type and update validation and tests (#1399)d8c6721fix large object upload and and update functional test for 0 byte file upload...bcbd469Update version to next releaseYou can trigger a rebase of this PR by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)